Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 634309d9b88fe3ff0a7275b88865d146cb574476a0a5f1a102d300a5315b8fdc

Tx prefix hash: a5994b2fa5b9d51988fba147e62407b8914d30f3253e6cd4323f8fd821d86a18
Tx public key: e60aac753f1a2b683f2de6f986ae7c791ff663681133d34da7619eda6ba5e714
Timestamp: 1728696015 Timestamp [UCT]: 2024-10-12 01:20:15 Age [y:d:h:m:s]: 00:103:13:22:15
Block: 1129656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73982 RingCT/type: yes/0
Extra: 01e60aac753f1a2b683f2de6f986ae7c791ff663681133d34da7619eda6ba5e7140211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f62f8041eb254fc9439d211eba69a0397024d51c52c7ed20f4b010f791e305c 0.600000000000 1612489 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": 1129666, "vin": [ { "gen": { "height": 1129656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f62f8041eb254fc9439d211eba69a0397024d51c52c7ed20f4b010f791e305c" } } ], "extra": [ 1, 230, 10, 172, 117, 63, 26, 43, 104, 63, 45, 230, 249, 134, 174, 124, 121, 31, 246, 99, 104, 17, 51, 211, 77, 167, 97, 158, 218, 107, 165, 231, 20, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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