Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a50ae04441ba2b1e122089fd336842bdf8e3dd2df19e3e67f985a80fb13de5

Tx prefix hash: 8bf7104f6a158c24d86977082a329a88cd0705f0d97407c8ca670e268db0a8f0
Tx public key: 100d7e6d720a32c8ef3318bb8550eea94fea1826adc3285ab1fc83396b3cc43d
Timestamp: 1729528949 Timestamp [UCT]: 2024-10-21 16:42:29 Age [y:d:h:m:s]: 01:021:01:50:36
Block: 1136510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273469 RingCT/type: yes/0
Extra: 01100d7e6d720a32c8ef3318bb8550eea94fea1826adc3285ab1fc83396b3cc43d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf56f13ca6e7a6b153425665ed6d39b908a6a7bb5cc9bb051105367bf76f62ed 0.600000000000 1619855 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": 1136520, "vin": [ { "gen": { "height": 1136510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf56f13ca6e7a6b153425665ed6d39b908a6a7bb5cc9bb051105367bf76f62ed" } } ], "extra": [ 1, 16, 13, 126, 109, 114, 10, 50, 200, 239, 51, 24, 187, 133, 80, 238, 169, 79, 234, 24, 38, 173, 195, 40, 90, 177, 252, 131, 57, 107, 60, 196, 61, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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