Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc3091136c79708a84ae8b9337db4f49eb020162b7a5f8406311e2e1d42565ba

Tx prefix hash: 49880dd3dbd1955cb44a21e2770294fe2eb31b13718c6f15feae4ffa76b679c1
Tx public key: a70dc06d52888eb799e8fb6d8e8daeff0138509283d57a5818edf4b8bdb7ae9e
Timestamp: 1745448499 Timestamp [UCT]: 2025-04-23 22:48:19 Age [y:d:h:m:s]: 00:210:20:34:11
Block: 1268016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148425 RingCT/type: yes/0
Extra: 01a70dc06d52888eb799e8fb6d8e8daeff0138509283d57a5818edf4b8bdb7ae9e02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ff867f5a5ec3a3124d7bce218db526cdca6a3d7971264bf34e1755107973e7f 0.600000000000 1755245 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": 1268026, "vin": [ { "gen": { "height": 1268016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ff867f5a5ec3a3124d7bce218db526cdca6a3d7971264bf34e1755107973e7f" } } ], "extra": [ 1, 167, 13, 192, 109, 82, 136, 142, 183, 153, 232, 251, 109, 142, 141, 174, 255, 1, 56, 80, 146, 131, 213, 122, 88, 24, 237, 244, 184, 189, 183, 174, 158, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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