Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1073749c2a6e00df72dd0b9a6c58dd3ea32427813bab003e7498752b7c026fd0

Tx prefix hash: c890f83771672d7812fbedb05624b7c71918f4a494eb2a307179397bd5c91505
Tx public key: 9774664d312a6ed6f8b21efa92974f3d7c4869b45cd719754ff1d3c74edd0a7c
Timestamp: 1745497678 Timestamp [UCT]: 2025-04-24 12:27:58 Age [y:d:h:m:s]: 00:210:06:55:29
Block: 1268433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148008 RingCT/type: yes/0
Extra: 019774664d312a6ed6f8b21efa92974f3d7c4869b45cd719754ff1d3c74edd0a7c0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16283a6c30d6d175eff8b01d339e22c614aacf2cce34966aa839274d96a34ccf 0.600000000000 1755662 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1268443, "vin": [ { "gen": { "height": 1268433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16283a6c30d6d175eff8b01d339e22c614aacf2cce34966aa839274d96a34ccf" } } ], "extra": [ 1, 151, 116, 102, 77, 49, 42, 110, 214, 248, 178, 30, 250, 146, 151, 79, 61, 124, 72, 105, 180, 92, 215, 25, 117, 79, 241, 211, 199, 78, 221, 10, 124, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8