Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82921ebea8c4049593f2ec6debe6b16301b704db975d5af60d764667ae392b0f

Tx prefix hash: c2c9ad73acfc835798b97c4c5d1cf4c7c236b7271e3ec5481eb8d5481ed4cfb9
Tx public key: 38f4186a7081304b31d5c3e560425ad6a4f857cc048c7a367b5e0b908d744435
Timestamp: 1706713331 Timestamp [UCT]: 2024-01-31 15:02:11 Age [y:d:h:m:s]: 01:282:03:06:48
Block: 947382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460439 RingCT/type: yes/0
Extra: 0138f4186a7081304b31d5c3e560425ad6a4f857cc048c7a367b5e0b908d74443502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f8853619a6399ee13f94189d09a0e163e397f521a466e1d5f23b65316cb8821 0.600000000000 1405730 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": 947392, "vin": [ { "gen": { "height": 947382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f8853619a6399ee13f94189d09a0e163e397f521a466e1d5f23b65316cb8821" } } ], "extra": [ 1, 56, 244, 24, 106, 112, 129, 48, 75, 49, 213, 195, 229, 96, 66, 90, 214, 164, 248, 87, 204, 4, 140, 122, 54, 123, 94, 11, 144, 141, 116, 68, 53, 2, 17, 0, 0, 0, 7, 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