Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13994d3bcd9a7f0748ea18a425e805e0279cca0328c719868f30314b7d19d5d1

Tx prefix hash: 744b1c0f18e46af175d604547cac1215119f2025b88466238f0e8547bc12686a
Tx public key: 761d48088c6d5aeb7053cc6837e652891a7fe663aad5f5273444f544d3d561fb
Timestamp: 1717109881 Timestamp [UCT]: 2024-05-30 22:58:01 Age [y:d:h:m:s]: 00:306:12:22:40
Block: 1033589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219076 RingCT/type: yes/0
Extra: 01761d48088c6d5aeb7053cc6837e652891a7fe663aad5f5273444f544d3d561fb0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c47fb1b759c238b309f69ffec7b98a6d281fc734ae06711071ad4e8d3c35b89a 0.600000000000 1502060 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": 1033599, "vin": [ { "gen": { "height": 1033589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c47fb1b759c238b309f69ffec7b98a6d281fc734ae06711071ad4e8d3c35b89a" } } ], "extra": [ 1, 118, 29, 72, 8, 140, 109, 90, 235, 112, 83, 204, 104, 55, 230, 82, 137, 26, 127, 230, 99, 170, 213, 245, 39, 52, 68, 245, 68, 211, 213, 97, 251, 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