Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a31ebc3b67dd3e6c73d83599b45843342787818c7abcb42478b4616a398ea5c2

Tx prefix hash: 07a8d5bedced946a8fcb4cb44b9b2fd68f9e0b3699bfb582479576e423fbd460
Tx public key: e16c201fe74c7fb54aa963b9dcc639b5fed61003aaf3369ea6171006acf7467f
Timestamp: 1696106663 Timestamp [UCT]: 2023-09-30 20:44:23 Age [y:d:h:m:s]: 02:035:07:49:45
Block: 859666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544885 RingCT/type: yes/0
Extra: 01e16c201fe74c7fb54aa963b9dcc639b5fed61003aaf3369ea6171006acf7467f021100000002bfa22221000000000000000000

1 output(s) for total of 0.870101105000 dcy

stealth address amount amount idx
00: 87dec684af543d73ec8c8dc2d8ce63fd5953feb6658b1fb3ee10735bec44ad45 0.870101105000 1313904 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": 859676, "vin": [ { "gen": { "height": 859666 } } ], "vout": [ { "amount": 870101105, "target": { "key": "87dec684af543d73ec8c8dc2d8ce63fd5953feb6658b1fb3ee10735bec44ad45" } } ], "extra": [ 1, 225, 108, 32, 31, 231, 76, 127, 181, 74, 169, 99, 185, 220, 198, 57, 181, 254, 214, 16, 3, 170, 243, 54, 158, 166, 23, 16, 6, 172, 247, 70, 127, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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