Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fcbd69b80c613fe4d5960cb46ddeabf13a6270e6e6518a5a3792491c1444241

Tx prefix hash: 3c07860fb87d8d27e0f50b9dad014010450c4dcf5206c695bb718d5377bc028f
Tx public key: 3c569c9f7051f0de6c5d7c6ebf4051023eedfbe95a370d82d8e271ea5ca82978
Timestamp: 1736676746 Timestamp [UCT]: 2025-01-12 10:12:26 Age [y:d:h:m:s]: 00:072:13:17:14
Block: 1195674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51614 RingCT/type: yes/0
Extra: 013c569c9f7051f0de6c5d7c6ebf4051023eedfbe95a370d82d8e271ea5ca829780211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a281b3d501498527bb0b467ba40150018c371f1ce56e15e8245e5610d11ba441 0.600000000000 1682265 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": 1195684, "vin": [ { "gen": { "height": 1195674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a281b3d501498527bb0b467ba40150018c371f1ce56e15e8245e5610d11ba441" } } ], "extra": [ 1, 60, 86, 156, 159, 112, 81, 240, 222, 108, 93, 124, 110, 191, 64, 81, 2, 62, 237, 251, 233, 90, 55, 13, 130, 216, 226, 113, 234, 92, 168, 41, 120, 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