Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747fa34b159f80af933afd890ac1e99e59296135ed3abcfbf008945efe10d3cf

Tx prefix hash: f8fddb7abe53556fff0ee2765206ac906dc66c3ff4a88a809773778acb3ef200
Tx public key: 363053b509d848e7e10fbfbb095c0e23c0d23ba90aafa3b9a13eb867046f104c
Timestamp: 1706017989 Timestamp [UCT]: 2024-01-23 13:53:09 Age [y:d:h:m:s]: 01:091:22:21:38
Block: 941605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326820 RingCT/type: yes/0
Extra: 01363053b509d848e7e10fbfbb095c0e23c0d23ba90aafa3b9a13eb867046f104c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54a7bf0f0d6116716db9ea87f50f6ca74c558dd7fc3d4c31e2ce3de8a1cf6b1e 0.600000000000 1399761 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": 941615, "vin": [ { "gen": { "height": 941605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54a7bf0f0d6116716db9ea87f50f6ca74c558dd7fc3d4c31e2ce3de8a1cf6b1e" } } ], "extra": [ 1, 54, 48, 83, 181, 9, 216, 72, 231, 225, 15, 191, 187, 9, 92, 14, 35, 192, 210, 59, 169, 10, 175, 163, 185, 161, 62, 184, 103, 4, 111, 16, 76, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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