Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 624d398cbaec93d8e69ae7620c3a57035be554fd600807e5860917fb7137fe7f

Tx prefix hash: d31d8f622142c433eab3cc3e7162f000e87c36ffb16ecec699b9201e95d6b40e
Tx public key: 5a7d4d64e9cf508d9647ce4dc5813abcb868f640e704c4805860eab37a174f54
Timestamp: 1676204544 Timestamp [UCT]: 2023-02-12 12:22:24 Age [y:d:h:m:s]: 02:066:05:31:00
Block: 695356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 568947 RingCT/type: yes/0
Extra: 015a7d4d64e9cf508d9647ce4dc5813abcb868f640e704c4805860eab37a174f540211000000035029cbac000000000000000000

1 output(s) for total of 3.047872785000 dcy

stealth address amount amount idx
00: faeff7aaa3d4990866e3cfa7b6f2cb893452d90b2ba4c1596b04f5540d1f4d11 3.047872785000 1138309 of 0

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": 695366, "vin": [ { "gen": { "height": 695356 } } ], "vout": [ { "amount": 3047872785, "target": { "key": "faeff7aaa3d4990866e3cfa7b6f2cb893452d90b2ba4c1596b04f5540d1f4d11" } } ], "extra": [ 1, 90, 125, 77, 100, 233, 207, 80, 141, 150, 71, 206, 77, 197, 129, 58, 188, 184, 104, 246, 64, 231, 4, 196, 128, 88, 96, 234, 179, 122, 23, 79, 84, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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