Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44da0b9857dcb4c22aa7967b4c35e7b747c1868fa55a9b35db91c27eb021e3a0

Tx prefix hash: 3f7063f74a1c791771d179c63c87ec295b696e3ac25b8a11d943af40b3ca5788
Tx public key: fab3e0e40c88249d601288f20dbd0a0b35478baf62f9d971b7dbc2ea3abe74a3
Timestamp: 1717959187 Timestamp [UCT]: 2024-06-09 18:53:07 Age [y:d:h:m:s]: 00:283:00:13:20
Block: 1040637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202264 RingCT/type: yes/0
Extra: 01fab3e0e40c88249d601288f20dbd0a0b35478baf62f9d971b7dbc2ea3abe74a302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04dcc292227de4b246a33bf5ae9cda75e1bddc2f62f9dce6623a31bf2b322bb1 0.600000000000 1509294 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": 1040647, "vin": [ { "gen": { "height": 1040637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04dcc292227de4b246a33bf5ae9cda75e1bddc2f62f9dce6623a31bf2b322bb1" } } ], "extra": [ 1, 250, 179, 224, 228, 12, 136, 36, 157, 96, 18, 136, 242, 13, 189, 10, 11, 53, 71, 139, 175, 98, 249, 217, 113, 183, 219, 194, 234, 58, 190, 116, 163, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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