Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9610cf6a4f99cfb84e78f1de2009cfa1bb39933aee58c9d0b4a3d8d5f53548a

Tx prefix hash: 564a4a8c66466bade8866cbcd44989dd1e8b455321111a88d9d1aea98995e63e
Tx public key: 849346444fcd50da365a51d9c77efad56811481e5fe5440edf302d9ba18c8d3e
Timestamp: 1583081875 Timestamp [UCT]: 2020-03-01 16:57:55 Age [y:d:h:m:s]: 05:003:19:21:34
Block: 74674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157272 RingCT/type: yes/0
Extra: 01849346444fcd50da365a51d9c77efad56811481e5fe5440edf302d9ba18c8d3e0211000001c90aca7173000000000000000000

1 output(s) for total of 347.196099144000 dcy

stealth address amount amount idx
00: bee5019e6d357887f66dd9f3c116cf4ec0ee33965f4597f6050019db61a37b86 347.196099144000 138137 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": 74684, "vin": [ { "gen": { "height": 74674 } } ], "vout": [ { "amount": 347196099144, "target": { "key": "bee5019e6d357887f66dd9f3c116cf4ec0ee33965f4597f6050019db61a37b86" } } ], "extra": [ 1, 132, 147, 70, 68, 79, 205, 80, 218, 54, 90, 81, 217, 199, 126, 250, 213, 104, 17, 72, 30, 95, 229, 68, 14, 223, 48, 45, 155, 161, 140, 141, 62, 2, 17, 0, 0, 1, 201, 10, 202, 113, 115, 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