Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3dc984783d46da507600f4ccfce3f050837612a30b0c728cf4232121f371969

Tx prefix hash: 8c2b56f340f36321ae443c5d318ea33e3223d65d9d6f2e6e504e9cb0bc4a11ad
Tx public key: 70f837208bc42eed93ae3a46b43025f972c144c01bbfd51571448f0f792cb2d6
Timestamp: 1713969919 Timestamp [UCT]: 2024-04-24 14:45:19 Age [y:d:h:m:s]: 00:260:14:16:06
Block: 1007561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186524 RingCT/type: yes/0
Extra: 0170f837208bc42eed93ae3a46b43025f972c144c01bbfd51571448f0f792cb2d60211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 434fd5fc3074361a0aeb5a8ef609acc5b97a3fdad884c5d9519dbf03fd5e61f1 0.600000000000 1468945 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": 1007571, "vin": [ { "gen": { "height": 1007561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "434fd5fc3074361a0aeb5a8ef609acc5b97a3fdad884c5d9519dbf03fd5e61f1" } } ], "extra": [ 1, 112, 248, 55, 32, 139, 196, 46, 237, 147, 174, 58, 70, 180, 48, 37, 249, 114, 193, 68, 192, 27, 191, 213, 21, 113, 68, 143, 15, 121, 44, 178, 214, 2, 17, 0, 0, 0, 2, 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