Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a13a5c50fdc2cc46ef7d3b1be12d3b7e4569d867e1d919791f52d0c0305f33da

Tx prefix hash: dd67fdb36c214f5bd6016da8b36f971bfdbd2be5bdb5ce3b241a35f88650f8a9
Tx public key: 58737007d216149076bd656f1f928296e906636e456e031e5d32379e0dab1e4d
Timestamp: 1704491117 Timestamp [UCT]: 2024-01-05 21:45:17 Age [y:d:h:m:s]: 01:123:07:26:31
Block: 928958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349260 RingCT/type: yes/0
Extra: 0158737007d216149076bd656f1f928296e906636e456e031e5d32379e0dab1e4d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d98327fcb8cac567e7d72bf9efcd3a48fefdaf84edc8d8810d91eeb12ea4b0e 0.600000000000 1386824 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": 928968, "vin": [ { "gen": { "height": 928958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d98327fcb8cac567e7d72bf9efcd3a48fefdaf84edc8d8810d91eeb12ea4b0e" } } ], "extra": [ 1, 88, 115, 112, 7, 210, 22, 20, 144, 118, 189, 101, 111, 31, 146, 130, 150, 233, 6, 99, 110, 69, 110, 3, 30, 93, 50, 55, 158, 13, 171, 30, 77, 2, 17, 0, 0, 0, 1, 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