Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a5ceccf686d7fe34d4bdd57354f316eb4cafebaa007c9b1f6435c21b0cf5f30

Tx prefix hash: 36a8578b29b5031b73a261dedc52cca3cd2ee6e2e79a679e9654e056863b5fa3
Tx public key: 186040d2e92257a5c75517aaac6bf7451789e3f8048bde4d61dd7eb3e91e7199
Timestamp: 1712688605 Timestamp [UCT]: 2024-04-09 18:50:05 Age [y:d:h:m:s]: 01:208:12:54:30
Block: 996921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407725 RingCT/type: yes/0
Extra: 01186040d2e92257a5c75517aaac6bf7451789e3f8048bde4d61dd7eb3e91e71990211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46ba26a6b29a7e682a71182f205a3623075ba2b66d9e30e368feb3e66a4ce767 0.600000000000 1457349 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": 996931, "vin": [ { "gen": { "height": 996921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46ba26a6b29a7e682a71182f205a3623075ba2b66d9e30e368feb3e66a4ce767" } } ], "extra": [ 1, 24, 96, 64, 210, 233, 34, 87, 165, 199, 85, 23, 170, 172, 107, 247, 69, 23, 137, 227, 248, 4, 139, 222, 77, 97, 221, 126, 179, 233, 30, 113, 153, 2, 17, 0, 0, 0, 1, 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