Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42e3f8bda95efcdf72a7039b67bfc88f0d842e52a6a0e316634d7a2d5ffc1760

Tx prefix hash: 5b1c2da780fab9bd4dd6392773f141e9575b04e0694624d25c5136aa7e4d1937
Tx public key: b1dbf5509e24a77f8219b6422ed4286d6cb794a6168420b01b1408d3f0ed7bfb
Timestamp: 1750829028 Timestamp [UCT]: 2025-06-25 05:23:48 Age [y:d:h:m:s]: 00:142:04:10:36
Block: 1312310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99551 RingCT/type: yes/0
Extra: 01b1dbf5509e24a77f8219b6422ed4286d6cb794a6168420b01b1408d3f0ed7bfb02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd653c03a1e0cbf3fc5bc9e766d62d33e283526ae3dda0aafab84062b12cf34c 0.600000000000 1799943 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": 1312320, "vin": [ { "gen": { "height": 1312310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd653c03a1e0cbf3fc5bc9e766d62d33e283526ae3dda0aafab84062b12cf34c" } } ], "extra": [ 1, 177, 219, 245, 80, 158, 36, 167, 127, 130, 25, 182, 66, 46, 212, 40, 109, 108, 183, 148, 166, 22, 132, 32, 176, 27, 20, 8, 211, 240, 237, 123, 251, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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