Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 003b8fb7200ed4b79e186df1e8535470601f1a0e425f1ef6bf2821be3697cd47

Tx prefix hash: 4885b7c10916332a6f174c6e49283a5c7aa29e4fd33f547fe8ea4fc85c551cd2
Tx public key: ae8339e994e0d724c4553e1874fec3ad8e438bbb6580588bbd2ffe5c3cc0e786
Timestamp: 1746836439 Timestamp [UCT]: 2025-05-10 00:20:39 Age [y:d:h:m:s]: 00:009:02:19:02
Block: 1279512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6501 RingCT/type: yes/0
Extra: 01ae8339e994e0d724c4553e1874fec3ad8e438bbb6580588bbd2ffe5c3cc0e7860211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e87c7433107cf2db418ca11f9fd674312ab497c61cbdb35998a86bb2ee1a75d 0.600000000000 1766889 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": 1279522, "vin": [ { "gen": { "height": 1279512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e87c7433107cf2db418ca11f9fd674312ab497c61cbdb35998a86bb2ee1a75d" } } ], "extra": [ 1, 174, 131, 57, 233, 148, 224, 215, 36, 196, 85, 62, 24, 116, 254, 195, 173, 142, 67, 139, 187, 101, 128, 88, 139, 189, 47, 254, 92, 60, 192, 231, 134, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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