Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ded046e928ead68f824edf5e6f5c28badd448f6909c54f2c60a67966e35ff5d2

Tx prefix hash: 06ea479552d922b5a66afa8fbf2cfd28511f4a116f1a9a182a0b6b1143562f13
Tx public key: 44b0ec5715a6a6f6fc12adc69c202e326aed3163d92f783d8bf84cff27fd9ab8
Timestamp: 1706504599 Timestamp [UCT]: 2024-01-29 05:03:19 Age [y:d:h:m:s]: 01:281:17:39:23
Block: 945652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460142 RingCT/type: yes/0
Extra: 0144b0ec5715a6a6f6fc12adc69c202e326aed3163d92f783d8bf84cff27fd9ab80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b67ab7add4ffb25aee23339c344cfeb1a77cfe606cf4baaf3ad480b169d4a916 0.600000000000 1403968 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": 945662, "vin": [ { "gen": { "height": 945652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b67ab7add4ffb25aee23339c344cfeb1a77cfe606cf4baaf3ad480b169d4a916" } } ], "extra": [ 1, 68, 176, 236, 87, 21, 166, 166, 246, 252, 18, 173, 198, 156, 32, 46, 50, 106, 237, 49, 99, 217, 47, 120, 61, 139, 248, 76, 255, 39, 253, 154, 184, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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