Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd3a6f4b5b479ffb1b03fadb7b2094fe549b02282151212ff1a901f69cd6e9f9

Tx prefix hash: dcc3829f64a6fd5d691404e7b0f72b6b32bc17b70e14e6798621d422afdc0886
Tx public key: 6c55da15d35e8595b6ee93714e9f16888be2e8ecedcff86af8458b4bb33e8b32
Timestamp: 1700614961 Timestamp [UCT]: 2023-11-22 01:02:41 Age [y:d:h:m:s]: 01:202:03:45:12
Block: 896844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405683 RingCT/type: yes/0
Extra: 016c55da15d35e8595b6ee93714e9f16888be2e8ecedcff86af8458b4bb33e8b3202110000000175e3f0e9000000000000000000

1 output(s) for total of 0.655214528000 dcy

stealth address amount amount idx
00: 511dce060bf4666eee6f6f0525108da70b0dd7b41a5db0f213074c1d2c5cb859 0.655214528000 1353187 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": 896854, "vin": [ { "gen": { "height": 896844 } } ], "vout": [ { "amount": 655214528, "target": { "key": "511dce060bf4666eee6f6f0525108da70b0dd7b41a5db0f213074c1d2c5cb859" } } ], "extra": [ 1, 108, 85, 218, 21, 211, 94, 133, 149, 182, 238, 147, 113, 78, 159, 22, 136, 139, 226, 232, 236, 237, 207, 248, 106, 248, 69, 139, 75, 179, 62, 139, 50, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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