Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bc09e1793eddeb46524b9bee95bcda2bc8113b993e0fb66cbeb8a45e284c908

Tx prefix hash: 72a9610431999d06e0c570c2589f0e5f650b6afb2468d8886f9b21b631a66620
Tx public key: ac5c0f5700e07918e5811515ce372cf1be47b8654349f2e69237fb65e1cb2642
Timestamp: 1722837009 Timestamp [UCT]: 2024-08-05 05:50:09 Age [y:d:h:m:s]: 00:231:05:11:29
Block: 1081066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165142 RingCT/type: yes/0
Extra: 01ac5c0f5700e07918e5811515ce372cf1be47b8654349f2e69237fb65e1cb2642021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d92b0a5c0350d3d471d61b012ca46b7e804d6cfc12e62391e8df1722094ab26 0.600000000000 1554667 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": 1081076, "vin": [ { "gen": { "height": 1081066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d92b0a5c0350d3d471d61b012ca46b7e804d6cfc12e62391e8df1722094ab26" } } ], "extra": [ 1, 172, 92, 15, 87, 0, 224, 121, 24, 229, 129, 21, 21, 206, 55, 44, 241, 190, 71, 184, 101, 67, 73, 242, 230, 146, 55, 251, 101, 225, 203, 38, 66, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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