Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20315e7d9330574d294a07699bd1d5142a7c36294d59888c5a20151f2b806428

Tx prefix hash: a2ae18ef5e86442c5c52b336c58ae618ebba557d614dce110970f79e26142f50
Tx public key: 5a40def9d7f1c40d71af509b4b1cf90bd1d6d88f9d4d7a65a746bd6e700401fd
Timestamp: 1755401165 Timestamp [UCT]: 2025-08-17 03:26:05 Age [y:d:h:m:s]: 00:065:01:46:54
Block: 1348246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46312 RingCT/type: yes/0
Extra: 015a40def9d7f1c40d71af509b4b1cf90bd1d6d88f9d4d7a65a746bd6e700401fd021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfc9aa12fd6c730425d71f8aab36ad88a4842cb1cf6676cf357ae6bd152eb1e1 0.600000000000 1836169 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": 1348256, "vin": [ { "gen": { "height": 1348246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfc9aa12fd6c730425d71f8aab36ad88a4842cb1cf6676cf357ae6bd152eb1e1" } } ], "extra": [ 1, 90, 64, 222, 249, 215, 241, 196, 13, 113, 175, 80, 155, 75, 28, 249, 11, 209, 214, 216, 143, 157, 77, 122, 101, 167, 70, 189, 110, 112, 4, 1, 253, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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