Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce1bac9cf6cc9e14e0e82820d9961201bc84889a555813d0abbd3e52b9e867da

Tx prefix hash: 722bf1665d7076548b0f41a90f4265d08f42f6ff42c57ec19424db935ec0b97a
Tx public key: 3c29bb1c9036677908e5f5080f97e491c4ae8c215e1f0cf9c01cbeed6a403ded
Timestamp: 1765101750 Timestamp [UCT]: 2025-12-07 10:02:30 Age [y:d:h:m:s]: 00:016:02:47:27
Block: 1428341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11527 RingCT/type: yes/0
Extra: 013c29bb1c9036677908e5f5080f97e491c4ae8c215e1f0cf9c01cbeed6a403ded021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6a74b224b1a784dce005cb1385114139911f1868981729fc96282d42175c91f 0.600000000000 1917058 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": 1428351, "vin": [ { "gen": { "height": 1428341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6a74b224b1a784dce005cb1385114139911f1868981729fc96282d42175c91f" } } ], "extra": [ 1, 60, 41, 187, 28, 144, 54, 103, 121, 8, 229, 245, 8, 15, 151, 228, 145, 196, 174, 140, 33, 94, 31, 12, 249, 192, 28, 190, 237, 106, 64, 61, 237, 2, 17, 0, 0, 0, 5, 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