Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e2100fe1b506747859044a2434fd57a35caa74bee40c1ee7e546843daf4c644

Tx prefix hash: 872f6d44511a476f4d69c8b4e79f305ea15b5384b726b42f6f60ac2dbc86ca60
Tx public key: aa0aa5e5de81146ccc677c800a71923e41c574d461e4de1ac6512ff68d7e7876
Timestamp: 1716900836 Timestamp [UCT]: 2024-05-28 12:53:56 Age [y:d:h:m:s]: 00:339:11:58:35
Block: 1031874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242642 RingCT/type: yes/0
Extra: 01aa0aa5e5de81146ccc677c800a71923e41c574d461e4de1ac6512ff68d7e78760211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb7379fc92eab027bc6ad8dfc1ce225c2ed1a01a878e22f107887af41c9b063d 0.600000000000 1500323 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": 1031884, "vin": [ { "gen": { "height": 1031874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb7379fc92eab027bc6ad8dfc1ce225c2ed1a01a878e22f107887af41c9b063d" } } ], "extra": [ 1, 170, 10, 165, 229, 222, 129, 20, 108, 204, 103, 124, 128, 10, 113, 146, 62, 65, 197, 116, 212, 97, 228, 222, 26, 198, 81, 47, 246, 141, 126, 120, 118, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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