Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98fdf7d1b610a981a8b08c0295c3642c6064a2e95391c5b9c2d82feeb6db4159

Tx prefix hash: 288166c4d4a94c6ca7f53c06b2edbba01a004ecbf277723faab6313002d7e5d4
Tx public key: 972d73d35738b5012256a59a0f1b71f713466cb31c2cda5bb003b36d09ffb7c8
Timestamp: 1665561899 Timestamp [UTC]: 2022-10-12 08:04:59 Age [y:d:h:m:s]: 04:040:18:29:05
Block: 607374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1075730 RingCT/type: yes/0
Extra: 01972d73d35738b5012256a59a0f1b71f713466cb31c2cda5bb003b36d09ffb7c802110000000ae7ace25d000000000000000000

1 output(s) for total of 0.005963728365 xmr

stealth address amount amount idx tag
00: 4ca65da85f810e9f764220eaa92b8ebac0d7d61bc0c2645f237c4a1f78851c35 0.005963728365 1044002 of 0 -

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 dinastycoin-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": 607384, "vin": [ { "gen": { "height": 607374 } } ], "vout": [ { "amount": 5963728365, "target": { "key": "4ca65da85f810e9f764220eaa92b8ebac0d7d61bc0c2645f237c4a1f78851c35" } } ], "extra": [ 1, 151, 45, 115, 211, 87, 56, 181, 1, 34, 86, 165, 154, 15, 27, 113, 247, 19, 70, 108, 179, 28, 44, 218, 91, 176, 3, 179, 109, 9, 255, 183, 200, 2, 17, 0, 0, 0, 10, 231, 172, 226, 93, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: