Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37ded8f80751305c1961d896963bde6b55d47885eca7da7f5f003d53f6a1456f

Tx prefix hash: a917c9f7399c5883c44c6f3c39cd2e1358bf83b1695970e7967daa3ed6408af5
Tx public key: 11b983a38f235ba40bd1cd56339c39de7d6a5d2960d31b7d397e07e7c9ac405b
Timestamp: 1712928115 Timestamp [UCT]: 2024-04-12 13:21:55 Age [y:d:h:m:s]: 00:319:07:47:35
Block: 998909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228293 RingCT/type: yes/0
Extra: 0111b983a38f235ba40bd1cd56339c39de7d6a5d2960d31b7d397e07e7c9ac405b02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07a5eadb8e7e440fbf410c7917615836926b53a8824fdd9b45cc86036f1e5a6a 0.600000000000 1459383 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": 998919, "vin": [ { "gen": { "height": 998909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07a5eadb8e7e440fbf410c7917615836926b53a8824fdd9b45cc86036f1e5a6a" } } ], "extra": [ 1, 17, 185, 131, 163, 143, 35, 91, 164, 11, 209, 205, 86, 51, 156, 57, 222, 125, 106, 93, 41, 96, 211, 27, 125, 57, 126, 7, 231, 201, 172, 64, 91, 2, 17, 0, 0, 0, 5, 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