Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2572b47722f62c8cd374874833d2a9e5488df4c43acadf5f12154742d8eace7d

Tx prefix hash: e4a5baa2b1a9a90fa8640c883bc4e0c5c04cc4b067b282f2cdb2ddb4a9665258
Tx public key: e7611c4afafd991ed273964e2e5ece6f252ad7e1f6aa0bafb696fa022d541cb7
Timestamp: 1688190130 Timestamp [UCT]: 2023-07-01 05:42:10 Age [y:d:h:m:s]: 01:318:03:59:37
Block: 794101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488560 RingCT/type: yes/0
Extra: 01e7611c4afafd991ed273964e2e5ece6f252ad7e1f6aa0bafb696fa022d541cb7021100000002faf35c9c000000000000000000

1 output(s) for total of 1.434874371000 dcy

stealth address amount amount idx
00: d39fde4326f1784578be1d99cf777cc09e4f592a01bfcd753a327d51c6627091 1.434874371000 1244822 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": 794111, "vin": [ { "gen": { "height": 794101 } } ], "vout": [ { "amount": 1434874371, "target": { "key": "d39fde4326f1784578be1d99cf777cc09e4f592a01bfcd753a327d51c6627091" } } ], "extra": [ 1, 231, 97, 28, 74, 250, 253, 153, 30, 210, 115, 150, 78, 46, 94, 206, 111, 37, 42, 215, 225, 246, 170, 11, 175, 182, 150, 250, 2, 45, 84, 28, 183, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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