Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 372d130a1ce3487e6ad071ed3fb931ed19968e46dfcfabcf750c7883e4fc941e

Tx prefix hash: af0fd63806e8f19995e1a4463f9637254a731009984ea89443fa676527736c09
Tx public key: 257b4dc4a3e4b098c419a5d6a804700ab1f5cf3c359e28b82d9e7267888d31fc
Timestamp: 1659028546 Timestamp [UCT]: 2022-07-28 17:15:46 Age [y:d:h:m:s]: 02:325:08:59:28
Block: 553684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 753671 RingCT/type: yes/0
Extra: 01257b4dc4a3e4b098c419a5d6a804700ab1f5cf3c359e28b82d9e7267888d31fc021100000027eae24e24000000000000000000

1 output(s) for total of 8.982871553000 dcy

stealth address amount amount idx
00: 4112541f4f6d5e739996615f14a3d6d2f76a368d330aab17a080c4c9d16c0a18 8.982871553000 985506 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": 553694, "vin": [ { "gen": { "height": 553684 } } ], "vout": [ { "amount": 8982871553, "target": { "key": "4112541f4f6d5e739996615f14a3d6d2f76a368d330aab17a080c4c9d16c0a18" } } ], "extra": [ 1, 37, 123, 77, 196, 163, 228, 176, 152, 196, 25, 165, 214, 168, 4, 112, 10, 177, 245, 207, 60, 53, 158, 40, 184, 45, 158, 114, 103, 136, 141, 49, 252, 2, 17, 0, 0, 0, 39, 234, 226, 78, 36, 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