Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d8a7293068db0b7f72b596702d37e9df74c38aac3493ce4efe9525bed636f57

Tx prefix hash: 91e96a0dd2eb26982e4922eca0ec634ddbfd9b7898d40c71421db7be06395832
Tx public key: de4337428c1e52fea47a274861706d07b9a6bc459808493cf783f7c6b023f733
Timestamp: 1675643649 Timestamp [UCT]: 2023-02-06 00:34:09 Age [y:d:h:m:s]: 01:255:12:42:03
Block: 690702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443607 RingCT/type: yes/0
Extra: 01de4337428c1e52fea47a274861706d07b9a6bc459808493cf783f7c6b023f7330211000000025029cbac000000000000000000

1 output(s) for total of 3.158038912000 dcy

stealth address amount amount idx
00: 356e367df69a96acd21ac793d34f019fd63667e59328fce01ae8f1b8d2a0aefc 3.158038912000 1133436 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": 690712, "vin": [ { "gen": { "height": 690702 } } ], "vout": [ { "amount": 3158038912, "target": { "key": "356e367df69a96acd21ac793d34f019fd63667e59328fce01ae8f1b8d2a0aefc" } } ], "extra": [ 1, 222, 67, 55, 66, 140, 30, 82, 254, 164, 122, 39, 72, 97, 112, 109, 7, 185, 166, 188, 69, 152, 8, 73, 60, 247, 131, 247, 198, 176, 35, 247, 51, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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