Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf116ca6653b624124490f99f96bf443c5be37339b3b470fb42c8c2b51727f7c

Tx prefix hash: 6571cdd5cee47d9b49d48185387facfba708c2032d6c4542adb6229ea815efe8
Tx public key: 0ec04512c7108e5b1969d19dcf3735a6ce4a34e443e77a97f385d5970c508c9b
Timestamp: 1763518297 Timestamp [UCT]: 2025-11-19 02:11:37 Age [y:d:h:m:s]: 00:009:03:45:36
Block: 1415219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6556 RingCT/type: yes/0
Extra: 010ec04512c7108e5b1969d19dcf3735a6ce4a34e443e77a97f385d5970c508c9b0211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a75de37c2186d3dcb640f7b2dc9062ae3a22f3a5a01147dd84d11866aa28e7b3 0.600000000000 1903716 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": 1415229, "vin": [ { "gen": { "height": 1415219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a75de37c2186d3dcb640f7b2dc9062ae3a22f3a5a01147dd84d11866aa28e7b3" } } ], "extra": [ 1, 14, 192, 69, 18, 199, 16, 142, 91, 25, 105, 209, 157, 207, 55, 53, 166, 206, 74, 52, 228, 67, 231, 122, 151, 243, 133, 213, 151, 12, 80, 140, 155, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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