Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b13c1e64d0363a47484c32e7d2f149b91f53212867b2b5c158dd2e421d7a35a

Tx prefix hash: 8cad2a98dff8db6451de19f51f111ecdef03504349d3838302d570f98bd99d59
Tx public key: c0d87eab6d54c59524dc66dca1a79c4224e33f485cd4650a6a67197bd00fe6dd
Timestamp: 1730772613 Timestamp [UCT]: 2024-11-05 02:10:13 Age [y:d:h:m:s]: 00:002:10:43:27
Block: 1146775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1759 RingCT/type: yes/0
Extra: 01c0d87eab6d54c59524dc66dca1a79c4224e33f485cd4650a6a67197bd00fe6dd021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df0401e8f82aed01f1e17f8aefa04d3ef059e69782e92756136087be7409dbde 0.600000000000 1631466 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": 1146785, "vin": [ { "gen": { "height": 1146775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df0401e8f82aed01f1e17f8aefa04d3ef059e69782e92756136087be7409dbde" } } ], "extra": [ 1, 192, 216, 126, 171, 109, 84, 197, 149, 36, 220, 102, 220, 161, 167, 156, 66, 36, 227, 63, 72, 92, 212, 101, 10, 106, 103, 25, 123, 208, 15, 230, 221, 2, 17, 0, 0, 0, 7, 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