Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff9daa5ae0ef218dd7f505f593482b23b3f181c505d976fbe25fdac17e2f56a1

Tx prefix hash: 1d9f7486d7670548b837c2096416c74782139b66b7c3f42110cd09c48ceb6881
Tx public key: 3bf7c5415dd0befaf4bbc9aa48ecf842262a4ba5eb1628232601ec01239b9e4b
Timestamp: 1746218590 Timestamp [UCT]: 2025-05-02 20:43:10 Age [y:d:h:m:s]: 00:235:07:44:13
Block: 1274392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165944 RingCT/type: yes/0
Extra: 013bf7c5415dd0befaf4bbc9aa48ecf842262a4ba5eb1628232601ec01239b9e4b02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8661b570579ad729040944c9d44a71cdc0b77b9cc49577e2e9df0e7a9631e823 0.600000000000 1761687 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": 1274402, "vin": [ { "gen": { "height": 1274392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8661b570579ad729040944c9d44a71cdc0b77b9cc49577e2e9df0e7a9631e823" } } ], "extra": [ 1, 59, 247, 197, 65, 93, 208, 190, 250, 244, 187, 201, 170, 72, 236, 248, 66, 38, 42, 75, 165, 235, 22, 40, 35, 38, 1, 236, 1, 35, 155, 158, 75, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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