Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd40eaf235e7a66e6f2b454dd28d245d49c6b0f084f683244320326c3a1311af

Tx prefix hash: db4197bcd8c6be3d889bf893230a09f406e6ccef98356f690e0ddc7f31af1f05
Tx public key: c43409c8284ee5d042e61cbaf2a97d8498452b21b88a1b71f5fc5dd1874c7544
Timestamp: 1729176042 Timestamp [UCT]: 2024-10-17 14:40:42 Age [y:d:h:m:s]: 00:238:20:56:37
Block: 1133630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170482 RingCT/type: yes/0
Extra: 01c43409c8284ee5d042e61cbaf2a97d8498452b21b88a1b71f5fc5dd1874c754402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e7ea6fce9830b5f1f2ea7e47446ae4379cf37d631c44bc65e3247786858394e 0.600000000000 1616807 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": 1133640, "vin": [ { "gen": { "height": 1133630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e7ea6fce9830b5f1f2ea7e47446ae4379cf37d631c44bc65e3247786858394e" } } ], "extra": [ 1, 196, 52, 9, 200, 40, 78, 229, 208, 66, 230, 28, 186, 242, 169, 125, 132, 152, 69, 43, 33, 184, 138, 27, 113, 245, 252, 93, 209, 135, 76, 117, 68, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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