Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df14e592f8ed2886defcc0eb8b3444c3cf919dd823f2c2bdd1d32ca46434765d

Tx prefix hash: 66ae7eecaa0593013123e05b714e94c3874c30f329e03f98feacca03be0826b9
Tx public key: 71b0e3e5cb7f7bbb7abb0534aba7fd84f5fc64ba64c580243e13465df4684f6a
Timestamp: 1736053027 Timestamp [UCT]: 2025-01-05 04:57:07 Age [y:d:h:m:s]: 00:164:23:05:43
Block: 1190517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117575 RingCT/type: yes/0
Extra: 0171b0e3e5cb7f7bbb7abb0534aba7fd84f5fc64ba64c580243e13465df4684f6a021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c7f97101b559cd1620aeb0f0971ad9feb5b3960eda17f174f71e030f949e9ee 0.600000000000 1677034 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": 1190527, "vin": [ { "gen": { "height": 1190517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c7f97101b559cd1620aeb0f0971ad9feb5b3960eda17f174f71e030f949e9ee" } } ], "extra": [ 1, 113, 176, 227, 229, 203, 127, 123, 187, 122, 187, 5, 52, 171, 167, 253, 132, 245, 252, 100, 186, 100, 197, 128, 36, 62, 19, 70, 93, 244, 104, 79, 106, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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