Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c5f6acddff8182edee28f8e14df73000bb879e987c2548a24e1d53c8a1942e

Tx prefix hash: 518fd0f96e460eb26e36f6670c8355f37f2cf68262186c22c5595e5f4d51e8d0
Tx public key: aecc33f16c5954d75f4823e783c48d61af625d259c7f09c8e0f455d10de8f925
Timestamp: 1625579014 Timestamp [UCT]: 2021-07-06 13:43:34 Age [y:d:h:m:s]: 03:197:18:52:08
Block: 289179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 911416 RingCT/type: yes/0
Extra: 01aecc33f16c5954d75f4823e783c48d61af625d259c7f09c8e0f455d10de8f925021100000002bffe00bb000000000000000000

1 output(s) for total of 67.581905921000 dcy

stealth address amount amount idx
00: 0322d97bd3a0ce7a9110eecb7aa08a40d63158fd809df65f6e9b163712e7aa0f 67.581905921000 605706 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": 289189, "vin": [ { "gen": { "height": 289179 } } ], "vout": [ { "amount": 67581905921, "target": { "key": "0322d97bd3a0ce7a9110eecb7aa08a40d63158fd809df65f6e9b163712e7aa0f" } } ], "extra": [ 1, 174, 204, 51, 241, 108, 89, 84, 215, 95, 72, 35, 231, 131, 196, 141, 97, 175, 98, 93, 37, 156, 127, 9, 200, 224, 244, 85, 209, 13, 232, 249, 37, 2, 17, 0, 0, 0, 2, 191, 254, 0, 187, 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