Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02d5d7ae98248e87ee5d11bd814afe9fd8ff994b820f9731382e9d46b67fc0e5

Tx prefix hash: 447ab78d6dbe9116ff6a3763d2a09af1caef79129a9007cb5e246f21b136401f
Tx public key: 3cd019305fdbe6e800a4220f669d016e63f2a4ff8d1510ff81312a44a6f220d6
Timestamp: 1707336757 Timestamp [UCT]: 2024-02-07 20:12:37 Age [y:d:h:m:s]: 01:069:21:10:45
Block: 952571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310992 RingCT/type: yes/0
Extra: 013cd019305fdbe6e800a4220f669d016e63f2a4ff8d1510ff81312a44a6f220d60211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e5afba11f388855f8b7ea89b59bd79986ca962219a3f0cb85db01af638ed4e9 0.600000000000 1411623 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": 952581, "vin": [ { "gen": { "height": 952571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e5afba11f388855f8b7ea89b59bd79986ca962219a3f0cb85db01af638ed4e9" } } ], "extra": [ 1, 60, 208, 25, 48, 95, 219, 230, 232, 0, 164, 34, 15, 102, 157, 1, 110, 99, 242, 164, 255, 141, 21, 16, 255, 129, 49, 42, 68, 166, 242, 32, 214, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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