Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f64fadf7f71a51e99579537c59bd6276f352669bec6af1a8fb2aefd76a429c32

Tx prefix hash: d9cd91b415a0a490c0f3d2f46533ed1f2be72a7e5c63474f1fc635d63f95b920
Tx public key: ed728f12ff0cc0f3016b7058c2783acefeb2d80e38f3045c8f2cb21b26b0f83e
Timestamp: 1720838387 Timestamp [UCT]: 2024-07-13 02:39:47 Age [y:d:h:m:s]: 00:256:03:37:26
Block: 1064521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182964 RingCT/type: yes/0
Extra: 01ed728f12ff0cc0f3016b7058c2783acefeb2d80e38f3045c8f2cb21b26b0f83e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88394164331e3bbc8f3405e06234c0108cb0fd28ac3494d9ea5527e32aacc241 0.600000000000 1535050 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": 1064531, "vin": [ { "gen": { "height": 1064521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88394164331e3bbc8f3405e06234c0108cb0fd28ac3494d9ea5527e32aacc241" } } ], "extra": [ 1, 237, 114, 143, 18, 255, 12, 192, 243, 1, 107, 112, 88, 194, 120, 58, 206, 254, 178, 216, 14, 56, 243, 4, 92, 143, 44, 178, 27, 38, 176, 248, 62, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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