Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48f38e704c3af8488e29bb1571ea73fe3c387790ea05ee886175082a86342f93

Tx prefix hash: 6749dc968044f472fd0093cc64cdb8f177fafcaf4e1db040695703e0ead1a8b3
Tx public key: 778669465d26131d2a6fff7e607f2d6ccf5f9ea4298138f8c3abf7a279a1885f
Timestamp: 1737912013 Timestamp [UCT]: 2025-01-26 17:20:13 Age [y:d:h:m:s]: 01:005:17:06:36
Block: 1205902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262363 RingCT/type: yes/0
Extra: 01778669465d26131d2a6fff7e607f2d6ccf5f9ea4298138f8c3abf7a279a1885f02110000000edfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5e1e2af371a10ebec2a3a443c066045c259e2bc88ef8e66c9e6b01de6bf20cc 0.600000000000 1692601 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": 1205912, "vin": [ { "gen": { "height": 1205902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5e1e2af371a10ebec2a3a443c066045c259e2bc88ef8e66c9e6b01de6bf20cc" } } ], "extra": [ 1, 119, 134, 105, 70, 93, 38, 19, 29, 42, 111, 255, 126, 96, 127, 45, 108, 207, 95, 158, 164, 41, 129, 56, 248, 195, 171, 247, 162, 121, 161, 136, 95, 2, 17, 0, 0, 0, 14, 223, 195, 186, 73, 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