Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdbb21427fe91b8f231c085685b243e0378f6524dab4852c10d9d4275188105a

Tx prefix hash: bf750f0b37eb02bc000a028d84f47aed7fbebf0ef1d05e322814ead1463ecd9f
Tx public key: 43cc6691b122a0da7eae2170a9a500c19aeba35347c47e95744b13e5943b8b6d
Timestamp: 1679014888 Timestamp [UCT]: 2023-03-17 01:01:28 Age [y:d:h:m:s]: 02:094:16:19:37
Block: 718659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589137 RingCT/type: yes/0
Extra: 0143cc6691b122a0da7eae2170a9a500c19aeba35347c47e95744b13e5943b8b6d0211000000025029cbac000000000000000000

1 output(s) for total of 2.551433711000 dcy

stealth address amount amount idx
00: 92210d468d9afa8e10febcc4c7bc1de4ca4713cec7a3e7aa3952d0fb4581cae2 2.551433711000 1163344 of 0

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": 718669, "vin": [ { "gen": { "height": 718659 } } ], "vout": [ { "amount": 2551433711, "target": { "key": "92210d468d9afa8e10febcc4c7bc1de4ca4713cec7a3e7aa3952d0fb4581cae2" } } ], "extra": [ 1, 67, 204, 102, 145, 177, 34, 160, 218, 126, 174, 33, 112, 169, 165, 0, 193, 154, 235, 163, 83, 71, 196, 126, 149, 116, 75, 19, 229, 148, 59, 139, 109, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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