Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6db354954785779fafce709e0e9efa45cb1cefe1ac093058fb1a8571a2ac4eb

Tx prefix hash: 369aad40b60b7adfe58ea937f69a16b7f692eb178a909500586b722679c5aed9
Tx public key: b21e902b30139eb9483ad0f86cb11893603f6fc38d41d2e262cf5d0a1e747af2
Timestamp: 1763579737 Timestamp [UCT]: 2025-11-19 19:15:37 Age [y:d:h:m:s]: 00:071:13:48:48
Block: 1415723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51081 RingCT/type: yes/0
Extra: 01b21e902b30139eb9483ad0f86cb11893603f6fc38d41d2e262cf5d0a1e747af2021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec9b5c8f4d0fb6d99855ab02437498b0adebbbdbeb79d076df2ce10496cb7b4d 0.600000000000 1904228 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": 1415733, "vin": [ { "gen": { "height": 1415723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec9b5c8f4d0fb6d99855ab02437498b0adebbbdbeb79d076df2ce10496cb7b4d" } } ], "extra": [ 1, 178, 30, 144, 43, 48, 19, 158, 185, 72, 58, 208, 248, 108, 177, 24, 147, 96, 63, 111, 195, 141, 65, 210, 226, 98, 207, 93, 10, 30, 116, 122, 242, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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