Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff2c8fa66b4b17b5aae69f64dde3b42389a68bb299ad216848c90072c8634f52

Tx prefix hash: bee9cf685908f851d10b5b05fce6c7c15f55ddeb0a9c435602f2dfeefa018d6e
Tx public key: 809b927f93791b8b5377cb27fc6ca7d215850922f775ed2a1fb823539bd76a3a
Timestamp: 1635638678 Timestamp [UCT]: 2021-10-31 00:04:38 Age [y:d:h:m:s]: 03:099:18:56:20
Block: 363967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 849588 RingCT/type: yes/0
Extra: 01809b927f93791b8b5377cb27fc6ca7d215850922f775ed2a1fb823539bd76a3a02110000000d1154028c000000000000000000

1 output(s) for total of 38.196770232000 dcy

stealth address amount amount idx
00: 065cfd4564f8b2d7017a4b79f8f80eaebe83a586eb22586a611c9ac8b65cc25f 38.196770232000 739555 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": 363977, "vin": [ { "gen": { "height": 363967 } } ], "vout": [ { "amount": 38196770232, "target": { "key": "065cfd4564f8b2d7017a4b79f8f80eaebe83a586eb22586a611c9ac8b65cc25f" } } ], "extra": [ 1, 128, 155, 146, 127, 147, 121, 27, 139, 83, 119, 203, 39, 252, 108, 167, 210, 21, 133, 9, 34, 247, 117, 237, 42, 31, 184, 35, 83, 155, 215, 106, 58, 2, 17, 0, 0, 0, 13, 17, 84, 2, 140, 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