Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb84722a09f33cad6c01bbbde9d1f48eddf7014a3696e1818075591c91cb994a

Tx prefix hash: 8a238003d1eadb4617a1a99eea74ef7b9876e40d562fa8cc38adb11cb716bf98
Tx public key: 4eee369a4fc87bcfb8a586bced25c8c2ead044298f6a6b6806a00c08d60dcbbf
Timestamp: 1729101178 Timestamp [UCT]: 2024-10-16 17:52:58 Age [y:d:h:m:s]: 01:014:18:33:36
Block: 1133001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268927 RingCT/type: yes/0
Extra: 014eee369a4fc87bcfb8a586bced25c8c2ead044298f6a6b6806a00c08d60dcbbf02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c42979fb599addab1ab5f8e2198e69cb4e6bb2cdcf224809b158cedd85d230c6 0.600000000000 1616064 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": 1133011, "vin": [ { "gen": { "height": 1133001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c42979fb599addab1ab5f8e2198e69cb4e6bb2cdcf224809b158cedd85d230c6" } } ], "extra": [ 1, 78, 238, 54, 154, 79, 200, 123, 207, 184, 165, 134, 188, 237, 37, 200, 194, 234, 208, 68, 41, 143, 106, 107, 104, 6, 160, 12, 8, 214, 13, 203, 191, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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