Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10da903de2cd17d5ec45ac185413a059b60dfa602528d42c6e37fb4a1789b1f1

Tx prefix hash: dbc60a2f6254fb24322f3c82041f3e558630ecd37d3af3002b09be2fa5504e52
Tx public key: 21d898b31bce0b48249ea78c71a430a097f55e540de3a049e9c873ba3554ef9b
Timestamp: 1735110111 Timestamp [UCT]: 2024-12-25 07:01:51 Age [y:d:h:m:s]: 00:097:02:15:15
Block: 1182714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69162 RingCT/type: yes/0
Extra: 0121d898b31bce0b48249ea78c71a430a097f55e540de3a049e9c873ba3554ef9b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3f470ca3d9784738d297e201d3cfba7d33fdc877b8dd44c46b04b0902d723f5 0.600000000000 1669149 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": 1182724, "vin": [ { "gen": { "height": 1182714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3f470ca3d9784738d297e201d3cfba7d33fdc877b8dd44c46b04b0902d723f5" } } ], "extra": [ 1, 33, 216, 152, 179, 27, 206, 11, 72, 36, 158, 167, 140, 113, 164, 48, 160, 151, 245, 94, 84, 13, 227, 160, 73, 233, 200, 115, 186, 53, 84, 239, 155, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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