Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6c85db2eb24529793119ee1c1158cdb24479c66b0c18103bcb9301d01e338ee

Tx prefix hash: 279c8a64bf278fb53dbd59719ade2ca8cce7e22bf8923e4b6672bfbad84f4b45
Tx public key: 410e746dc2d2c0b6618fd267a64dc43b34dc2b2847503263107f1c202812e8dc
Timestamp: 1719081628 Timestamp [UCT]: 2024-06-22 18:40:28 Age [y:d:h:m:s]: 00:246:23:47:25
Block: 1049929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176468 RingCT/type: yes/0
Extra: 01410e746dc2d2c0b6618fd267a64dc43b34dc2b2847503263107f1c202812e8dc02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55ca156148f13ea41eec03327f88443afe830200c775bc8d30316cc5a8898d31 0.600000000000 1520046 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": 1049939, "vin": [ { "gen": { "height": 1049929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55ca156148f13ea41eec03327f88443afe830200c775bc8d30316cc5a8898d31" } } ], "extra": [ 1, 65, 14, 116, 109, 194, 210, 192, 182, 97, 143, 210, 103, 166, 77, 196, 59, 52, 220, 43, 40, 71, 80, 50, 99, 16, 127, 28, 32, 40, 18, 232, 220, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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