Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c1f382b9e80958246d4b8898900bb11e9e050607e332c0a70d5f392e35bece1

Tx prefix hash: 6435a3a74827f8a61f595df3652337fa46ee3405c4b95512adbfa72f2c013aa3
Tx public key: 99c087fbd742003e0cacf0ec04bf8a0ee914173893b98f06d7cbb98b716cfa1b
Timestamp: 1672264447 Timestamp [UCT]: 2022-12-28 21:54:07 Age [y:d:h:m:s]: 01:341:11:26:07
Block: 662660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505092 RingCT/type: yes/0
Extra: 0199c087fbd742003e0cacf0ec04bf8a0ee914173893b98f06d7cbb98b716cfa1b021100000001e7ace25d000000000000000000

1 output(s) for total of 3.911400660000 dcy

stealth address amount amount idx
00: b07e5693613eab86d45caf21bfe700b723ed5319668370eb786c6c55eac0a6b0 3.911400660000 1103525 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": 662670, "vin": [ { "gen": { "height": 662660 } } ], "vout": [ { "amount": 3911400660, "target": { "key": "b07e5693613eab86d45caf21bfe700b723ed5319668370eb786c6c55eac0a6b0" } } ], "extra": [ 1, 153, 192, 135, 251, 215, 66, 0, 62, 12, 172, 240, 236, 4, 191, 138, 14, 233, 20, 23, 56, 147, 185, 143, 6, 215, 203, 185, 139, 113, 108, 250, 27, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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