Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5278aa14161055223a91135ea4c1096ac689ef1b931efe789c7986d2b4bffd8

Tx prefix hash: 150fef7aefc285d19c5ef46d1c3d33511af1312505c0b28225a967622b6d64a9
Tx public key: 63b7dc684e3f55a80e4679ce6c1092647d6b73596e9e9b32c3fce3c08d9318d3
Timestamp: 1657709583 Timestamp [UCT]: 2022-07-13 10:53:03 Age [y:d:h:m:s]: 02:250:12:34:07
Block: 542834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 700198 RingCT/type: yes/0
Extra: 0163b7dc684e3f55a80e4679ce6c1092647d6b73596e9e9b32c3fce3c08d9318d3021100000002e6d27f9c000000000000000000

1 output(s) for total of 9.758111128000 dcy

stealth address amount amount idx
00: e52d0c55b5f97e63e9f557e185ae10f7aadcb456dc88295ebf70106e11d947fb 9.758111128000 973437 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": 542844, "vin": [ { "gen": { "height": 542834 } } ], "vout": [ { "amount": 9758111128, "target": { "key": "e52d0c55b5f97e63e9f557e185ae10f7aadcb456dc88295ebf70106e11d947fb" } } ], "extra": [ 1, 99, 183, 220, 104, 78, 63, 85, 168, 14, 70, 121, 206, 108, 16, 146, 100, 125, 107, 115, 89, 110, 158, 155, 50, 195, 252, 227, 192, 141, 147, 24, 211, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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