Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f66943cf48fbbceb2e7ebe3b0974b00e217dc023e9e6c0820bb1ca5e8e73bd9

Tx prefix hash: 06c7cd32adc41f687ddd2e12f0d8a15eca48a393fe1a34069abe1458032af3e9
Tx public key: d75bb2b847b1395bb38654bc5849c7c5ee7a425383c3e40b962be373a7e34690
Timestamp: 1707652429 Timestamp [UCT]: 2024-02-11 11:53:49 Age [y:d:h:m:s]: 01:061:07:41:16
Block: 955180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304875 RingCT/type: yes/0
Extra: 01d75bb2b847b1395bb38654bc5849c7c5ee7a425383c3e40b962be373a7e3469002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f6b0b9d88facd3b13c84fd7ed5f42a0360cb83fc0432082551ffe38a2060a73 0.600000000000 1414466 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": 955190, "vin": [ { "gen": { "height": 955180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f6b0b9d88facd3b13c84fd7ed5f42a0360cb83fc0432082551ffe38a2060a73" } } ], "extra": [ 1, 215, 91, 178, 184, 71, 177, 57, 91, 179, 134, 84, 188, 88, 73, 199, 197, 238, 122, 66, 83, 131, 195, 228, 11, 150, 43, 227, 115, 167, 227, 70, 144, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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