Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 402237f17c39a394faee09c041828b1afa2d8de2ccf61e305bb1189ee4c0b975

Tx prefix hash: b216224c7054e151b7ee5299efd14794e27e7871ea0bf73f75c77ed498b77e5a
Tx public key: 3af1c91b9853bf1151b1ba4eef21b46dff98547292ea50162049b7a073ff0c9e
Timestamp: 1723992078 Timestamp [UCT]: 2024-08-18 14:41:18 Age [y:d:h:m:s]: 01:124:13:10:32
Block: 1090657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347541 RingCT/type: yes/0
Extra: 013af1c91b9853bf1151b1ba4eef21b46dff98547292ea50162049b7a073ff0c9e02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 834f91b2d83356efaeb9e426489a3db56b62663befbb8b8d38f8bbb0ce306863 0.600000000000 1565280 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": 1090667, "vin": [ { "gen": { "height": 1090657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "834f91b2d83356efaeb9e426489a3db56b62663befbb8b8d38f8bbb0ce306863" } } ], "extra": [ 1, 58, 241, 201, 27, 152, 83, 191, 17, 81, 177, 186, 78, 239, 33, 180, 109, 255, 152, 84, 114, 146, 234, 80, 22, 32, 73, 183, 160, 115, 255, 12, 158, 2, 17, 0, 0, 0, 13, 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