Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61b73f4661d7297afb654225f0f12f30ce56de5b51692b447ad5aecd6792d5e4

Tx prefix hash: c3cbdc05080b7c5ce4c9a2b571ea1d3a59a958f62e55c6e95190715eae800dc2
Tx public key: 2ca4e3ce1615b24aabf1e193f5944a67253a708f1aaa20ba0874c7a9127e09cf
Timestamp: 1698517116 Timestamp [UCT]: 2023-10-28 18:18:36 Age [y:d:h:m:s]: 01:173:02:28:12
Block: 879666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384725 RingCT/type: yes/0
Extra: 012ca4e3ce1615b24aabf1e193f5944a67253a708f1aaa20ba0874c7a9127e09cf02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.746966953000 dcy

stealth address amount amount idx
00: d0b266391a4503e9e6a266e6c7a800ba502983224af3bd20b3ba3d202d5e7992 0.746966953000 1335200 of 0

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": 879676, "vin": [ { "gen": { "height": 879666 } } ], "vout": [ { "amount": 746966953, "target": { "key": "d0b266391a4503e9e6a266e6c7a800ba502983224af3bd20b3ba3d202d5e7992" } } ], "extra": [ 1, 44, 164, 227, 206, 22, 21, 178, 74, 171, 241, 225, 147, 245, 148, 74, 103, 37, 58, 112, 143, 26, 170, 32, 186, 8, 116, 199, 169, 18, 126, 9, 207, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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