Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3fb2e5873422e3e42da78c5435a65dfa514e900a1fd00f81f120b4a1c3ff019

Tx prefix hash: 6bc15412a5c9eb448741a8e4ebe259322a02af0054bcd0471521d6e034c94ba7
Tx public key: 4d8b295ed88fa07878fd2656bfffe48a2369633805d3dff469d94df7f616c11f
Timestamp: 1718838019 Timestamp [UCT]: 2024-06-19 23:00:19 Age [y:d:h:m:s]: 01:150:23:07:49
Block: 1047924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366450 RingCT/type: yes/0
Extra: 014d8b295ed88fa07878fd2656bfffe48a2369633805d3dff469d94df7f616c11f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8638f0902b2f18e54bdfabb5ce5334d3a4e340f1d6c4ea9c660e62f6482316b 0.600000000000 1517875 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": 1047934, "vin": [ { "gen": { "height": 1047924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8638f0902b2f18e54bdfabb5ce5334d3a4e340f1d6c4ea9c660e62f6482316b" } } ], "extra": [ 1, 77, 139, 41, 94, 216, 143, 160, 120, 120, 253, 38, 86, 191, 255, 228, 138, 35, 105, 99, 56, 5, 211, 223, 244, 105, 217, 77, 247, 246, 22, 193, 31, 2, 17, 0, 0, 0, 2, 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