Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5805783a6d8c89493f3769851794dbc3df1064d2294811aab395a9bdf9e619f8

Tx prefix hash: 0ba78c1afba42e2b48acbf2c09c77baad436a1c82dc4f4ae3d165ca4217acfa0
Tx public key: 8be6f04ce2d2bdc737a0438ae6b02a9b20eeccfb11e592dfda23946990a18565
Timestamp: 1726810797 Timestamp [UCT]: 2024-09-20 05:39:57 Age [y:d:h:m:s]: 00:155:22:16:12
Block: 1114024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111220 RingCT/type: yes/0
Extra: 018be6f04ce2d2bdc737a0438ae6b02a9b20eeccfb11e592dfda23946990a18565021100000002bdafe9cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 250b7fb31eb02945ec4fc2be792e567ca51b20bddf3f2d4c2f9f2d799f24916c 0.600000000000 1593821 of 15

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": 1114034, "vin": [ { "gen": { "height": 1114024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250b7fb31eb02945ec4fc2be792e567ca51b20bddf3f2d4c2f9f2d799f24916c" } } ], "extra": [ 1, 139, 230, 240, 76, 226, 210, 189, 199, 55, 160, 67, 138, 230, 176, 42, 155, 32, 238, 204, 251, 17, 229, 146, 223, 218, 35, 148, 105, 144, 161, 133, 101, 2, 17, 0, 0, 0, 2, 189, 175, 233, 204, 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