Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60f40836a728c90b80898f33d779e24cef903fadfa506d8078ed692b21f642e3

Tx prefix hash: 499d078f3b5f6dc73f5c529d0394216433e9cfbb84358af6afbd3b0381c687e7
Tx public key: 009cf409483702e05d9d73e2de91116e6ec9c9f80c81ce9bd8730a9a9aff5397
Timestamp: 1731040268 Timestamp [UCT]: 2024-11-08 04:31:08 Age [y:d:h:m:s]: 00:073:03:21:07
Block: 1149003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52269 RingCT/type: yes/0
Extra: 01009cf409483702e05d9d73e2de91116e6ec9c9f80c81ce9bd8730a9a9aff53970211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0f6ce10219e30987d7b42664e26afe3d403c4b804f6b6b0a8d1484705b873f9 0.600000000000 1633982 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": 1149013, "vin": [ { "gen": { "height": 1149003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0f6ce10219e30987d7b42664e26afe3d403c4b804f6b6b0a8d1484705b873f9" } } ], "extra": [ 1, 0, 156, 244, 9, 72, 55, 2, 224, 93, 157, 115, 226, 222, 145, 17, 110, 110, 201, 201, 248, 12, 129, 206, 155, 216, 115, 10, 154, 154, 255, 83, 151, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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