Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95b1deae8cdf1ed562c3129e20931300e5e92584a2811caad351484122f2eba2

Tx prefix hash: a3b59784fda7cb79a14c79fc3238a1c44635407f1bf38587bbb608ad3cf31212
Tx public key: 233e8503bdc081277554c74a4cdd5dc71f5c623e074d0ebfd722986c5a92e03f
Timestamp: 1737170405 Timestamp [UCT]: 2025-01-18 03:20:05 Age [y:d:h:m:s]: 00:058:09:07:12
Block: 1199753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41516 RingCT/type: yes/0
Extra: 01233e8503bdc081277554c74a4cdd5dc71f5c623e074d0ebfd722986c5a92e03f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f826fea445f8eae6269bbeddd61fa68cab500164bb9a3dc638e2f09acd9ed62a 0.600000000000 1686386 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": 1199763, "vin": [ { "gen": { "height": 1199753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f826fea445f8eae6269bbeddd61fa68cab500164bb9a3dc638e2f09acd9ed62a" } } ], "extra": [ 1, 35, 62, 133, 3, 189, 192, 129, 39, 117, 84, 199, 74, 76, 221, 93, 199, 31, 92, 98, 62, 7, 77, 14, 191, 215, 34, 152, 108, 90, 146, 224, 63, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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