Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61d9bd9d183dc724120d0e13bd67f8d6ff9ae7525ee1cfae76fd404a80ddf92b

Tx prefix hash: 2b10487971cedd173e3e8d725cda7ea3d62f5a41580c8655cf1601e8728c559c
Tx public key: 725caf551647fdde0d1a1288ca09d17dcd49628242539b3ba0baf21f6a233ae0
Timestamp: 1581823537 Timestamp [UCT]: 2020-02-16 03:25:37 Age [y:d:h:m:s]: 05:086:01:46:45
Block: 65919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214452 RingCT/type: yes/0
Extra: 01725caf551647fdde0d1a1288ca09d17dcd49628242539b3ba0baf21f6a233ae002110000000312c4732d000000000000000000

1 output(s) for total of 371.179342715000 dcy

stealth address amount amount idx
00: 3fbdcadaf30c8f8a52b8eaf990d875355b928498a597dbcbbc4806641f4e5613 371.179342715000 121544 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": 65929, "vin": [ { "gen": { "height": 65919 } } ], "vout": [ { "amount": 371179342715, "target": { "key": "3fbdcadaf30c8f8a52b8eaf990d875355b928498a597dbcbbc4806641f4e5613" } } ], "extra": [ 1, 114, 92, 175, 85, 22, 71, 253, 222, 13, 26, 18, 136, 202, 9, 209, 125, 205, 73, 98, 130, 66, 83, 155, 59, 160, 186, 242, 31, 106, 35, 58, 224, 2, 17, 0, 0, 0, 3, 18, 196, 115, 45, 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