Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 195475b43d0a515487c4f5e7b708bc1cb0db95d26280e11e8afd522443d499b1

Tx prefix hash: df35e04e7c0234c3743a7b83c09f268f2483116d0856c472f460030500d57c4c
Tx public key: 09358e139c8a339e4715de708911acc6627a30e3bf9e98f17f1a948a43978736
Timestamp: 1746373321 Timestamp [UCT]: 2025-05-04 15:42:01 Age [y:d:h:m:s]: 00:191:18:09:35
Block: 1275679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134753 RingCT/type: yes/0
Extra: 0109358e139c8a339e4715de708911acc6627a30e3bf9e98f17f1a948a439787360211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd2a03e8809aa6fd78601dcfbfa242b16ffeb45bed55b45a4a8b28a5cdc8b2dc 0.600000000000 1762994 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": 1275689, "vin": [ { "gen": { "height": 1275679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd2a03e8809aa6fd78601dcfbfa242b16ffeb45bed55b45a4a8b28a5cdc8b2dc" } } ], "extra": [ 1, 9, 53, 142, 19, 156, 138, 51, 158, 71, 21, 222, 112, 137, 17, 172, 198, 98, 122, 48, 227, 191, 158, 152, 241, 127, 26, 148, 138, 67, 151, 135, 54, 2, 17, 0, 0, 0, 6, 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