Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e53a594efe238abfe6d2a9b18f4a89dadbc1f939d02433b3e698415a522c5b94

Tx prefix hash: 4b42c6e5740726ec912d72f1004db6458e2b99f5612711173134b8bb4e9082eb
Tx public key: 37d4c89c57ab832005eea46509b51192f9766a3b6b08e1004773fbe8fca239b7
Timestamp: 1735676587 Timestamp [UCT]: 2024-12-31 20:23:07 Age [y:d:h:m:s]: 00:166:17:55:46
Block: 1187386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118900 RingCT/type: yes/0
Extra: 0137d4c89c57ab832005eea46509b51192f9766a3b6b08e1004773fbe8fca239b7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d49d251e331f42d9ef28faff41f4ff4d495f092ab08b61b0b9e824a1786e15a 0.600000000000 1673875 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": 1187396, "vin": [ { "gen": { "height": 1187386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d49d251e331f42d9ef28faff41f4ff4d495f092ab08b61b0b9e824a1786e15a" } } ], "extra": [ 1, 55, 212, 200, 156, 87, 171, 131, 32, 5, 238, 164, 101, 9, 181, 17, 146, 249, 118, 106, 59, 107, 8, 225, 0, 71, 115, 251, 232, 252, 162, 57, 183, 2, 17, 0, 0, 0, 4, 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