Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e07e79aa29f5cd21f0ef958d0fe29b604c5992c1eb7726f150957d0c8fedf4ef

Tx prefix hash: 823df6693df5b248c86ea8c05a60d24e0fe57c2f2a1b41dc3191054f45507183
Tx public key: 2f26f2414fa47fe83993336afb6c3e4ce6479d8d68a14e69afa7279539dfcbf4
Timestamp: 1742177018 Timestamp [UCT]: 2025-03-17 02:03:38 Age [y:d:h:m:s]: 00:238:21:18:34
Block: 1240951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168452 RingCT/type: yes/0
Extra: 012f26f2414fa47fe83993336afb6c3e4ce6479d8d68a14e69afa7279539dfcbf4021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fae277c548c5a435603ee9c801f4a1357e1342a59f6124b0d136c558a6922917 0.600000000000 1727924 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": 1240961, "vin": [ { "gen": { "height": 1240951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fae277c548c5a435603ee9c801f4a1357e1342a59f6124b0d136c558a6922917" } } ], "extra": [ 1, 47, 38, 242, 65, 79, 164, 127, 232, 57, 147, 51, 106, 251, 108, 62, 76, 230, 71, 157, 141, 104, 161, 78, 105, 175, 167, 39, 149, 57, 223, 203, 244, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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