Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5660a824d25b73b49a22d241d8222d441e004ed9e43ffe08d30f895f8529dd02

Tx prefix hash: 4c9af4c1a87bf7461773f036ae0ece961b70b2216db2e07f9ec469e525e0939e
Tx public key: d30a721b3f56d6128cb12468d910d47b494f83735bf05941e91c0c8c5669a87a
Timestamp: 1706507688 Timestamp [UCT]: 2024-01-29 05:54:48 Age [y:d:h:m:s]: 01:030:17:37:59
Block: 945673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283014 RingCT/type: yes/0
Extra: 01d30a721b3f56d6128cb12468d910d47b494f83735bf05941e91c0c8c5669a87a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3772d0df318597220a8789e0f34ca23c23a9a5636017f0ae3c108788d18cc01 0.600000000000 1403989 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": 945683, "vin": [ { "gen": { "height": 945673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3772d0df318597220a8789e0f34ca23c23a9a5636017f0ae3c108788d18cc01" } } ], "extra": [ 1, 211, 10, 114, 27, 63, 86, 214, 18, 140, 177, 36, 104, 217, 16, 212, 123, 73, 79, 131, 115, 91, 240, 89, 65, 233, 28, 12, 140, 86, 105, 168, 122, 2, 17, 0, 0, 0, 1, 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