Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7858b99def5675ebca70e24a7ce6576900efc9b4f190a26c07b0cdb8df6c1bc2

Tx prefix hash: 21c020bc79b2b36ae26e0b34a224aa7a5a1fbe8137eb98ca57b8cb1fccfb9bc5
Tx public key: 36d66ae95bf7ea6530997fdf02174467ed9db2953bdd2392ed4a0ee94b393458
Timestamp: 1725424138 Timestamp [UCT]: 2024-09-04 04:28:58 Age [y:d:h:m:s]: 00:261:18:20:07
Block: 1102525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186967 RingCT/type: yes/0
Extra: 0136d66ae95bf7ea6530997fdf02174467ed9db2953bdd2392ed4a0ee94b39345802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beb4f9a1a3091690196c11da4fe158a3fdf0a714f94b2684b27e2532cc149c3c 0.600000000000 1578996 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": 1102535, "vin": [ { "gen": { "height": 1102525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beb4f9a1a3091690196c11da4fe158a3fdf0a714f94b2684b27e2532cc149c3c" } } ], "extra": [ 1, 54, 214, 106, 233, 91, 247, 234, 101, 48, 153, 127, 223, 2, 23, 68, 103, 237, 157, 178, 149, 59, 221, 35, 146, 237, 74, 14, 233, 75, 57, 52, 88, 2, 17, 0, 0, 0, 3, 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