Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 536ed5cfb6c3cfd3fbf0ac691af33979b3428456f28dc43af270f131af0c4d5a

Tx prefix hash: ac256fd374e313e8134962b241256230aaf8ce1aa2763563db1d37c170d479e4
Tx public key: d4a935b12992cf765ff7f1ee6115b9d12031e91985f7d50766c6c7dcac098a35
Timestamp: 1702750254 Timestamp [UCT]: 2023-12-16 18:10:54 Age [y:d:h:m:s]: 01:187:01:32:22
Block: 914548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394711 RingCT/type: yes/0
Extra: 01d4a935b12992cf765ff7f1ee6115b9d12031e91985f7d50766c6c7dcac098a35021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ad915f9ae86ed40a3d532f2d26a203fe4aacbad4b7ab2678ea3e70afa1f07c4 0.600000000000 1371874 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": 914558, "vin": [ { "gen": { "height": 914548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ad915f9ae86ed40a3d532f2d26a203fe4aacbad4b7ab2678ea3e70afa1f07c4" } } ], "extra": [ 1, 212, 169, 53, 177, 41, 146, 207, 118, 95, 247, 241, 238, 97, 21, 185, 209, 32, 49, 233, 25, 133, 247, 213, 7, 102, 198, 199, 220, 172, 9, 138, 53, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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