Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08eacc686b45e0a413357cac4f4735e5d9728d8d65784a97be4b5237a400c926

Tx prefix hash: 2f86f17b068ffd0e61df5d96e6135f61d2d42a0aface13b2253749a1bebb25e2
Tx public key: 57362485dc6ae9d42aeeced2e632c634621248e81d39d4d770bfa27f4e447b96
Timestamp: 1714030498 Timestamp [UCT]: 2024-04-25 07:34:58 Age [y:d:h:m:s]: 00:257:07:29:33
Block: 1008058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184189 RingCT/type: yes/0
Extra: 0157362485dc6ae9d42aeeced2e632c634621248e81d39d4d770bfa27f4e447b960211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cde91632a633c3b49e9697b2e6b168791633bb296e0d7f2a0b6763eb28e39918 0.600000000000 1469524 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": 1008068, "vin": [ { "gen": { "height": 1008058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cde91632a633c3b49e9697b2e6b168791633bb296e0d7f2a0b6763eb28e39918" } } ], "extra": [ 1, 87, 54, 36, 133, 220, 106, 233, 212, 42, 238, 206, 210, 230, 50, 198, 52, 98, 18, 72, 232, 29, 57, 212, 215, 112, 191, 162, 127, 78, 68, 123, 150, 2, 17, 0, 0, 0, 3, 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