Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3ca4ff74f369757633273c3a4cd46f7a70ec40aa9620478ce6406e99dfd7e82

Tx prefix hash: 5850dcc645a2b355d4d9d22740210f7620a3754a4aea57e15d5a4631be7e06d9
Tx public key: af526e86fcd19f73d688a1dd590ba2cc08323fde8ba974d86fa6d158d3e9542d
Timestamp: 1709577317 Timestamp [UCT]: 2024-03-04 18:35:17 Age [y:d:h:m:s]: 00:357:11:31:09
Block: 971151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255586 RingCT/type: yes/0
Extra: 01af526e86fcd19f73d688a1dd590ba2cc08323fde8ba974d86fa6d158d3e9542d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fbe04b53134c0f653f45d522b5102be32a2a144e3428171be9ee2bdf024b84f 0.600000000000 1431036 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": 971161, "vin": [ { "gen": { "height": 971151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fbe04b53134c0f653f45d522b5102be32a2a144e3428171be9ee2bdf024b84f" } } ], "extra": [ 1, 175, 82, 110, 134, 252, 209, 159, 115, 214, 136, 161, 221, 89, 11, 162, 204, 8, 50, 63, 222, 139, 169, 116, 216, 111, 166, 209, 88, 211, 233, 84, 45, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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