Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e12c7cdb2a927694a22ee5997ac0cb83a4a3887e9d2c2f67ab3755e29fc36dc

Tx prefix hash: 5526cfcc8e17bfe343eb799745b241c4102e0c7377aed89765870d5480daf267
Tx public key: 7d3bf461096840c26af1fa6047eef0e30d4c33f2fe231848e54abac4706242d2
Timestamp: 1577886160 Timestamp [UCT]: 2020-01-01 13:42:40 Age [y:d:h:m:s]: 04:329:08:53:57
Block: 36364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124623 RingCT/type: yes/0
Extra: 017d3bf461096840c26af1fa6047eef0e30d4c33f2fe231848e54abac4706242d2021100000015398c17aa000000000000000000

1 output(s) for total of 465.063039348000 dcy

stealth address amount amount idx
00: 567592d7138fd332e1147beff131b5e337438758acc474ff4849b0a021d46dce 465.063039348000 61583 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": 36374, "vin": [ { "gen": { "height": 36364 } } ], "vout": [ { "amount": 465063039348, "target": { "key": "567592d7138fd332e1147beff131b5e337438758acc474ff4849b0a021d46dce" } } ], "extra": [ 1, 125, 59, 244, 97, 9, 104, 64, 194, 106, 241, 250, 96, 71, 238, 240, 227, 13, 76, 51, 242, 254, 35, 24, 72, 229, 74, 186, 196, 112, 98, 66, 210, 2, 17, 0, 0, 0, 21, 57, 140, 23, 170, 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