Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45bdcc8da06ff23668628346f124f0ffb4ba517bdf1f57a645ed2563cf120c91

Tx prefix hash: 717a79205f9b4b5f0f1eb33fb679ff2e2b8708be9d45dcdd1af592bc233caf15
Tx public key: 7238677359b4599ae6462c27b1129a6d2ac55d9b6dbde5d0da6d0c4ac3ebd7fc
Timestamp: 1710047925 Timestamp [UCT]: 2024-03-10 05:18:45 Age [y:d:h:m:s]: 01:266:20:00:39
Block: 975056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449437 RingCT/type: yes/0
Extra: 017238677359b4599ae6462c27b1129a6d2ac55d9b6dbde5d0da6d0c4ac3ebd7fc0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02b9f091d35b32ba585ba565906fc0f3f3c2edc42d217cd239868bc4f47fcb12 0.600000000000 1435027 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": 975066, "vin": [ { "gen": { "height": 975056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02b9f091d35b32ba585ba565906fc0f3f3c2edc42d217cd239868bc4f47fcb12" } } ], "extra": [ 1, 114, 56, 103, 115, 89, 180, 89, 154, 230, 70, 44, 39, 177, 18, 154, 109, 42, 197, 93, 155, 109, 189, 229, 208, 218, 109, 12, 74, 195, 235, 215, 252, 2, 17, 0, 0, 0, 2, 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