Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d2fb161e91eb1007285584ba4db77b6c851a3388f29f36e900e93c80df49bf8

Tx prefix hash: c1a56af3584a9bf787001105546522afcb54c948d43b9f8f49a6a25175133a26
Tx public key: f2a714b84801f5a4f14649bd6adeda2a1e3768a9dc4d293092bcc036e8abe30b
Timestamp: 1733455539 Timestamp [UCT]: 2024-12-06 03:25:39 Age [y:d:h:m:s]: 00:034:18:50:03
Block: 1169005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24883 RingCT/type: yes/0
Extra: 01f2a714b84801f5a4f14649bd6adeda2a1e3768a9dc4d293092bcc036e8abe30b0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 066797b466bd626a1ebc849c2541028ea607c407621345efae84b99a23a7f575 0.600000000000 1654718 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": 1169015, "vin": [ { "gen": { "height": 1169005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "066797b466bd626a1ebc849c2541028ea607c407621345efae84b99a23a7f575" } } ], "extra": [ 1, 242, 167, 20, 184, 72, 1, 245, 164, 241, 70, 73, 189, 106, 222, 218, 42, 30, 55, 104, 169, 220, 77, 41, 48, 146, 188, 192, 54, 232, 171, 227, 11, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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