Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3efb03877d0a9b44e7538f79597bdd013a75b31c64a482e11172061f545f11c8

Tx prefix hash: eaca328bf99f575637253517d92a7ccb8cbbc7ea361d7b56ef21187770122dd0
Tx public key: e82f7364631bb3ab4f991dc83dd455ce13550550256eaaa32a3ecea3d68a5f8b
Timestamp: 1734252914 Timestamp [UCT]: 2024-12-15 08:55:14 Age [y:d:h:m:s]: 00:094:02:43:43
Block: 1175624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67052 RingCT/type: yes/0
Extra: 01e82f7364631bb3ab4f991dc83dd455ce13550550256eaaa32a3ecea3d68a5f8b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8480a6f875e9ea0d71746d19c1c115b5d09cf77fcfe7f2f9929a56e8dee5d909 0.600000000000 1661929 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": 1175634, "vin": [ { "gen": { "height": 1175624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8480a6f875e9ea0d71746d19c1c115b5d09cf77fcfe7f2f9929a56e8dee5d909" } } ], "extra": [ 1, 232, 47, 115, 100, 99, 27, 179, 171, 79, 153, 29, 200, 61, 212, 85, 206, 19, 85, 5, 80, 37, 110, 170, 163, 42, 62, 206, 163, 214, 138, 95, 139, 2, 17, 0, 0, 0, 1, 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