Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdb432bdf2c1577c6548fd4ca8b54c17a4ce43143a195ab278ae857c3d5610f1

Tx prefix hash: 2c6e4ba51b77c8d2c678907d8d961da37db449beba7c67206dc7a5b11f857851
Tx public key: b8e87faf27f4abf5fc84fba6ac93f93d0160e7f87946d02a30c882747083b8ac
Timestamp: 1748169897 Timestamp [UCT]: 2025-05-25 10:44:57 Age [y:d:h:m:s]: 00:178:21:38:06
Block: 1290563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125551 RingCT/type: yes/0
Extra: 01b8e87faf27f4abf5fc84fba6ac93f93d0160e7f87946d02a30c882747083b8ac0211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c13388794758557fe2ad06adc7e7e242be41fb138624ad268b21784322d28bfe 0.600000000000 1778032 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": 1290573, "vin": [ { "gen": { "height": 1290563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c13388794758557fe2ad06adc7e7e242be41fb138624ad268b21784322d28bfe" } } ], "extra": [ 1, 184, 232, 127, 175, 39, 244, 171, 245, 252, 132, 251, 166, 172, 147, 249, 61, 1, 96, 231, 248, 121, 70, 208, 42, 48, 200, 130, 116, 112, 131, 184, 172, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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