Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e816e3911e245b92c48e114a1ee7f7505e79c50a22da5b2d5770f9e963b0dc55

Tx prefix hash: 7ce7e5c1095115f1d163969448d660666615de5b5db85b9ff004f077ad2197c2
Tx public key: 97387b679bf1f627e81a23f872bd2dfc9b23d9be480d250240e2df58ea439c9b
Timestamp: 1763603965 Timestamp [UCT]: 2025-11-20 01:59:25 Age [y:d:h:m:s]: 00:033:11:30:22
Block: 1415930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23953 RingCT/type: yes/0
Extra: 0197387b679bf1f627e81a23f872bd2dfc9b23d9be480d250240e2df58ea439c9b02110000000117b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b7025a20d6704e8a5aefaeeffae26a01eaa378b94dfa6f53ef965a1e26b86de 0.600000000000 1904441 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": 1415940, "vin": [ { "gen": { "height": 1415930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b7025a20d6704e8a5aefaeeffae26a01eaa378b94dfa6f53ef965a1e26b86de" } } ], "extra": [ 1, 151, 56, 123, 103, 155, 241, 246, 39, 232, 26, 35, 248, 114, 189, 45, 252, 155, 35, 217, 190, 72, 13, 37, 2, 64, 226, 223, 88, 234, 67, 156, 155, 2, 17, 0, 0, 0, 1, 23, 177, 145, 50, 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