Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 434e5fc9b2211895ba568fec234aa40ba5d45331dc11771ad16b7e4ff5c14f1f

Tx prefix hash: 24dbaa2b6c957c1c8ad59211266f6070bb2d57d28e5ac4f710aaaa7f2427fcbb
Tx public key: 596939bccc50aaa2430f3d8f0dd28d242ebf8061a79f9f7fa429c87e64b96ce1
Timestamp: 1717970245 Timestamp [UCT]: 2024-06-09 21:57:25 Age [y:d:h:m:s]: 00:143:17:20:23
Block: 1040721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102875 RingCT/type: yes/0
Extra: 01596939bccc50aaa2430f3d8f0dd28d242ebf8061a79f9f7fa429c87e64b96ce10211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bfe7f4e9451487291428f8d3b3aea018c070e4bc79a4580b0bd0fcb3020c710 0.600000000000 1509380 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": 1040731, "vin": [ { "gen": { "height": 1040721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bfe7f4e9451487291428f8d3b3aea018c070e4bc79a4580b0bd0fcb3020c710" } } ], "extra": [ 1, 89, 105, 57, 188, 204, 80, 170, 162, 67, 15, 61, 143, 13, 210, 141, 36, 46, 191, 128, 97, 167, 159, 159, 127, 164, 41, 200, 126, 100, 185, 108, 225, 2, 17, 0, 0, 0, 7, 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