Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aabeab101e284133878107e3860b938b9bb682a147f3c508ce7914b8c153243

Tx prefix hash: 23469377a9ce64f1b0ec80f70845396000c1b14f5c732d09821e64c742ebdcd8
Tx public key: 39fbb6e01ee4c16e2f02ff5c5593d9755ecaa6a0cf9a98d948f07983d5c84a81
Timestamp: 1713330379 Timestamp [UCT]: 2024-04-17 05:06:19 Age [y:d:h:m:s]: 00:314:01:06:52
Block: 1002241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224498 RingCT/type: yes/0
Extra: 0139fbb6e01ee4c16e2f02ff5c5593d9755ecaa6a0cf9a98d948f07983d5c84a810211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e42c3a93a4f2fc077fe247f4bd983fd93ae88f64cea577bfe2f822d2821f85c 0.600000000000 1462757 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": 1002251, "vin": [ { "gen": { "height": 1002241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e42c3a93a4f2fc077fe247f4bd983fd93ae88f64cea577bfe2f822d2821f85c" } } ], "extra": [ 1, 57, 251, 182, 224, 30, 228, 193, 110, 47, 2, 255, 92, 85, 147, 217, 117, 94, 202, 166, 160, 207, 154, 152, 217, 72, 240, 121, 131, 213, 200, 74, 129, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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