Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75a8eff09b43cdf6b85d37e3852c9a367b35a66155f5a831cf8b2b31bdf57f46

Tx prefix hash: fddae67b9836f8fb66800442310e996656930c6eef97858a8351c0db16a80b2c
Tx public key: 79e8b57c8172cf86dc486bbdae63db0dc53566b0a275e808841f42df24b11f31
Timestamp: 1717277675 Timestamp [UCT]: 2024-06-01 21:34:35 Age [y:d:h:m:s]: 00:303:00:07:16
Block: 1035002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216537 RingCT/type: yes/0
Extra: 0179e8b57c8172cf86dc486bbdae63db0dc53566b0a275e808841f42df24b11f3102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dd553d5a68653b2a5766728a54a030e995f6e663b75d3424e0c85fdf6df27e3 0.600000000000 1503521 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": 1035012, "vin": [ { "gen": { "height": 1035002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dd553d5a68653b2a5766728a54a030e995f6e663b75d3424e0c85fdf6df27e3" } } ], "extra": [ 1, 121, 232, 181, 124, 129, 114, 207, 134, 220, 72, 107, 189, 174, 99, 219, 13, 197, 53, 102, 176, 162, 117, 232, 8, 132, 31, 66, 223, 36, 177, 31, 49, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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