Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4343ef43d90456d0d691ef323b30dd08cedf98458f3d553882e0cf04703b64f6

Tx prefix hash: fb561757d2233df383b82240c0addc9f6362b3e2dac5d541d0330e7aa4af9985
Tx public key: b50d33f556eec6972c8a906055021d8bd3149174d4e81d4853bcd293e34090e8
Timestamp: 1578452928 Timestamp [UCT]: 2020-01-08 03:08:48 Age [y:d:h:m:s]: 04:317:21:11:49
Block: 40941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116526 RingCT/type: yes/0
Extra: 01b50d33f556eec6972c8a906055021d8bd3149174d4e81d4853bcd293e34090e80211000000168a2ee0d9000000000000000000

1 output(s) for total of 449.103374018000 dcy

stealth address amount amount idx
00: 8f2cffe7d8dcb3a095fbd7b5db6a7ccf00867d85bef0e0e0928b9e2675b2b663 449.103374018000 72429 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": 40951, "vin": [ { "gen": { "height": 40941 } } ], "vout": [ { "amount": 449103374018, "target": { "key": "8f2cffe7d8dcb3a095fbd7b5db6a7ccf00867d85bef0e0e0928b9e2675b2b663" } } ], "extra": [ 1, 181, 13, 51, 245, 86, 238, 198, 151, 44, 138, 144, 96, 85, 2, 29, 139, 211, 20, 145, 116, 212, 232, 29, 72, 83, 188, 210, 147, 227, 64, 144, 232, 2, 17, 0, 0, 0, 22, 138, 46, 224, 217, 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