Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848808d8979d49fd880e74fb4fe79cdf6b6ddbf1dd9f19fa3a9986b224e4fb52

Tx prefix hash: a9533d6ba70bbae4a93d517f098489cc125b6fda448af2d1c1b3fec02e82a606
Tx public key: 29eaecf12e91303dfe08fb2e90b6f445e8a6a5ca5a7d8fd9714e25b9c6b12416
Timestamp: 1707343591 Timestamp [UCT]: 2024-02-07 22:06:31 Age [y:d:h:m:s]: 01:056:12:17:33
Block: 952630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301436 RingCT/type: yes/0
Extra: 0129eaecf12e91303dfe08fb2e90b6f445e8a6a5ca5a7d8fd9714e25b9c6b1241602110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e136e3d04d6510b77071d8732ca6c8143cf6c08b324392e59e46b877c09838df 0.600000000000 1411714 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": 952640, "vin": [ { "gen": { "height": 952630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e136e3d04d6510b77071d8732ca6c8143cf6c08b324392e59e46b877c09838df" } } ], "extra": [ 1, 41, 234, 236, 241, 46, 145, 48, 61, 254, 8, 251, 46, 144, 182, 244, 69, 232, 166, 165, 202, 90, 125, 143, 217, 113, 78, 37, 185, 198, 177, 36, 22, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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