Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f26449ac66fbbe86194180f0068fec76664b9218c2fd6ce0d84ce428673f6191

Tx prefix hash: 2a10c7de9146e0f99a5cf7e56a02ceb32916d8217641b898a5c42c486d36f297
Tx public key: 18a7b47b319f410ceba99a940c195d1f262cf6bf9a49251382fe8bac1e9a7435
Timestamp: 1746858804 Timestamp [UCT]: 2025-05-10 06:33:24 Age [y:d:h:m:s]: 00:151:01:13:55
Block: 1279701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105602 RingCT/type: yes/0
Extra: 0118a7b47b319f410ceba99a940c195d1f262cf6bf9a49251382fe8bac1e9a74350211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4a2b3a8b54e4478d125c8d7633c7d627eeb32f5211920cc87a62e1ece4ac2b1 0.600000000000 1767080 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": 1279711, "vin": [ { "gen": { "height": 1279701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4a2b3a8b54e4478d125c8d7633c7d627eeb32f5211920cc87a62e1ece4ac2b1" } } ], "extra": [ 1, 24, 167, 180, 123, 49, 159, 65, 12, 235, 169, 154, 148, 12, 25, 93, 31, 38, 44, 246, 191, 154, 73, 37, 19, 130, 254, 139, 172, 30, 154, 116, 53, 2, 17, 0, 0, 0, 4, 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