Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e06af92ff11860a3a6b5d01398110b125fba56481718e3051d77809eb8777a6

Tx prefix hash: af9aa533806b3eef26cbbb77f36258ba1a1dede6b5f30bfc3f6023f1ef93646f
Tx public key: 7261ee054dfbe982fbba9cba096b47dffe34c8ba6e000c2955f0bf9f16ef9cad
Timestamp: 1705365290 Timestamp [UCT]: 2024-01-16 00:34:50 Age [y:d:h:m:s]: 01:152:18:38:38
Block: 936206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370223 RingCT/type: yes/0
Extra: 017261ee054dfbe982fbba9cba096b47dffe34c8ba6e000c2955f0bf9f16ef9cad0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f1fee8c3615ae68fd89b98f9cb73440a4017553bba3b4f355fcbe45fb6a1f5 0.600000000000 1394230 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": 936216, "vin": [ { "gen": { "height": 936206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f1fee8c3615ae68fd89b98f9cb73440a4017553bba3b4f355fcbe45fb6a1f5" } } ], "extra": [ 1, 114, 97, 238, 5, 77, 251, 233, 130, 251, 186, 156, 186, 9, 107, 71, 223, 254, 52, 200, 186, 110, 0, 12, 41, 85, 240, 191, 159, 22, 239, 156, 173, 2, 17, 0, 0, 0, 1, 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